Columbia Kermit/kermit.zip/newsgroups/misc.19990422-19990725/[e-mail] _Wed May 26 12:22:56 1999.msg

Internet Message Format | 2020-01-01 | 2KB

Return-Path: <[e-mail]>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.59.30])
    by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id MAA21399
    for <[e-mail]>; Wed, 26 May 1999 12:22:52 -0400 (EDT)
Received: (from news@localhost)
    by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id MAA13069
    for [e-mail]; Wed, 26 May 1999 12:00:05 -0400 (EDT)
X-Authentication-Warning: newsmaster.cc.columbia.edu: news set sender to <news> using -f
From: "Mr. Scott" <[e-mail]>
Subject: Re: kermit process hangs around after terminal disconnect
Date: Wed, 26 May 1999 14:55:32 GMT
Organization: Deja.com - Share what you know. Learn what you don't.
Message-ID: <7ih212$rvs$[e-mail]>
To: [e-mail]

Thank you for responding.
Yes, it pretty much is a Procomm->UNIX issue because the shell is
hanging around.  I'm just incredulous that UNIX doesn't swiftly detect
the broken connection; instead, waiting hours, days, or sometimes what
seems like forever to finally realize that no-one is on the other end
of a telnet connection.  What's up with that?  Can you explain why such
dumbness would happen?  I program sockets a bit, and it was my
understanding that "send", "recv", or whatever returns a zero to
indicate EOF when a TCP connection is broken.  All the server programs
I have written detect this condition immediately as the client shuts
down, dies, terminates, whatever.  Why doesn't the UNIX telnet/pty
server program do the same?


--== Sent via Deja.com http://www.deja.com/ ==--
---Share what you know. Learn what you don't.---